connectGatt is successful without previous gatt not being closed#620
Merged
philips77 merged 1 commit intonordicsemi:mainfrom Jun 5, 2025
Merged
Conversation
… being called resulting resources allocated for gatt is not released until the application is stopped/killed
junebeans
changed the title
connectGatt is successful without previous gatt not being closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In some cases, there were race condition where the previous gatt was not closed, but
bluetoothGattgets overridden due to the nextconnectGattcall being executed. With this previous gatt client not closed - it remains in memory keep consuming assigned seat for ble gatt on operating system.This pull request ensures to close the gatt object before the next
connectGattis executed.